Bump version of autorest adal, so builds are possible again#1267
Open
MB175 wants to merge 1 commit intogolang-migrate:masterfrom
Open
Bump version of autorest adal, so builds are possible again#1267MB175 wants to merge 1 commit intogolang-migrate:masterfrom
MB175 wants to merge 1 commit intogolang-migrate:masterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The github.com/Azure/go-autorest/autorest/adal module version previously used has been retracted due to token refresh errors. To address this, we've updated the dependency to a non-retracted version.
Updated Dependency: autorest/adal bumped to version v0.9.24
Reason for Update: Previous version was retracted due to token refresh issues.
Temporary Workaround: This update serves as a temporary solution to avoid immediate migration to the module's successor.
For more details on the retraction, refer to the discussion in issue #1266 .